-
Notifications
You must be signed in to change notification settings - Fork 292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds interface type to ROS2 message type name #191
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not very familiar with the bridge, but this looks okay to me with green CI.
Amazing, got non reproducible test failures -.- |
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
2b5b0fa
to
435a954
Compare
Update: there are actually more tests failing - across all rmw impl. |
Merging this in order to release a first version into Dashing |
Topic bridging tests are OK but service bridging ones I was unable to reproduce, and that was happening before the rebase :( |
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com> Signed-off-by: Dhananjay Sathe <dhananjay.sathe@rapyuta-robotics.com>
Fixes ros2/build_farmer#192. This pull request fixes ros1 bridge mapping factory template to take into account the interface type in the message type name.
Another one to be added to the list in ros2/ros2#677.